> Ah, using OWL and the STL. Unfortunately, there seems to be a conflict
> with how OWL uses the old Borland string class and the STL string class.The code snippet I included did not contain any reference to OWL, "STL string class" or
Borland string class. The project settings I showed did have the OWL library checked, but
none of the OWL code was pulled in by including vector.h.
There is a problem with the compiler which causes an internal error message to be generated
when the project is built as I described and the 3 line program is compiled. I verified
this with Borland support.
> Have you tried using explicit scoping or a using-declaration instead of
> the catch-all using-directive? The former two are recommended over the
> latter, anyways.
> That's not the point. I can make the problem go away by turning off the Rogue Wave
namespace usage altogether. But, my point at the time I wrote the post was to verify that
the compiler was broken, and that it wasn't my system. Now that I got a tech person at
Borland to follow the same steps, and it happened to him, I can assume the problem is with
the compiler, which means I can stop removing it and reinstalling it, hoping something will
change.
--
Martin Moore email: moore@tdl.com
FlexSoft //// Technical Analysis and Quote Downloaders
Technical Analysis Scanner (TAS) & Personal Ticker Tape (PTT)
